For Microsoft environment the best option of WebServices
Hosting websites on-premises or in the cloud, Microsoft IIS is the best choice for deploying websites using Microsoft technology such as AS…
Overview
What is Microsoft IIS?
Microsoft IIS is an application server and infrastructure.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Installation (28)9.090%
- Application server performance (28)8.080%
- Administration and management (28)8.080%
- Security management (28)7.070%
Pricing
N/A
Unavailable
What is Microsoft IIS?
Microsoft IIS is an application server and infrastructure.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
73 people also want pricing
Alternatives Pricing
What is NGINX Plus?
NGINX Plus is presented as a cloud‑native, easy-to-use reverse proxy, load balancer, and API gateway, from F5.
What is Zend Server?
Zend Server, developed by Zend, acquired by Rogue Wave Software in 2017 and then by Perforce in 2019 with that company's acquisition of Rogue Wave, is an All-in-One PHP Application Server that aims to improve web app deployment, debugging, and monitoring. Additionally, ZendPHP Enterprise offers…
Product Demos
Microsoft Internet Information Service Training
YouTube
[日本語: Japanese] CVE-2017-7269 IIS 6.0 WebDAV ScStoragePathFromUrl 0day Metasploit Demo
YouTube
Features
Return to navigation
Product Details
- About
- Tech Details
- FAQs
What is Microsoft IIS?
Microsoft IIS Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Frequently Asked Questions
Microsoft IIS is an application server and infrastructure.
Reviewers rate Installation highest, with a score of 9.
The most common users of Microsoft IIS are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(86)Attribute Ratings
Reviews
(1-5 of 5)Companies can't remove reviews or game the system. Here's why
Microsoft IIS is being used by my organization to serve business and scientific applications for users in the organization and externally. The applications are a mixture of ASP.NET, .NET MVC, and more recently .NET Core. It is an integral part of our IT services, and each instance often serves over 10 applications.
- Microsoft familiarity
- Already on most Windows machines
- Fairly easy to setup a .NET application in it
- Fairly robust
- Complicated to configure if it's not out of the box
- Shuts down app pools and applications after a certain amount of non-use time and makes it hard to stop this behavior--this makes running scheduled tasks with something like Hangfire in your app more difficult (you often need to pull this out into a Windows service or something), which I think is unnecessary
- Quite slow when compared to modern open-source servers
- Logging errors and things in EventViewer is hell--considering EventViewer on an under load Windows server can barely draw itself in under five minutes
- Unlikable interface
- Serves multiple applications quite well
- Fairly easy to set up
- Well supported by Microsoft
- Microsoft familiarity
- Already on Windows Server machines
46.66666666666667%
4.7
- Improved time to market for some applications due to quick setup times
- Re-use of existing infrastructure
- Saves money
After using both Microsoft IIS and free Linux alternatives, like NGINX and Apache, I have to say I much prefer the Linux products in every way. Configuration is clearer (you have to edit config files deep in Linux somewhere, but once you've done it once, it's easy). Logging is better and simpler (no awful EventViewer). NGINX and Apache tend to be much faster, more robust, and they don't shut anything down--they serve things forever. Microsoft IIS is continually shutting things down and then when the next request comes in, it takes too long to get things running again to serve it.
September 25, 2020
Microsoft IIS can handle simple to complex hosting requirements
IIS is being used by our organization to host all of our internal and external web sites and applications. All users in our company use IIS by using our applications. We are using IIS for both simple and complex applications which the company relies on. A big problem it has solved is allowing us to integrate it with TFS allowing for seamless and highly efficient changes to occur on our applications when requested by the business.
- A big advantage that we use all the time is reviewing the logs that automatically get generated in IIS. It has helped us troubleshoot various problems in our applications over the years.
- IIS integrates really well with Visual Studio and TFS. We are able to quickly deploy new applications and changes to applications when requested by the business.
- IIS has proven that it is easy to configure and maintain with minimal effort.
- There have been times where we have been concerned about the security vulnerabilities that IIS has been exposed to.
- Logging in IIS is good but at times the error message are quite vague or point us in the wrong direction. More succinct and clear error messages would be nice.
- Configuring IIS as a reverse proxy server has too many steps and is confusing at times.
83.33333333333334%
8.3
- We have been able to quickly setup and deploy applications using IIS which has allowed the business to engage customers more quickly.
- IIS has failed us at times when an issue occurs and the default error messaging has not been clear which caused us to look for issues in the wrong place.
- Creating a separate app pool for each web site, which is default in IIS, saved us from causing the entire server to crash when memory leaks occurred.
We have always been a IIS company so we haven't used any other products like it.
September 21, 2019
Microsoft IIS Server - Honest review by a FullStack developer
We use Microsoft IIS for specific requirements on client deliverables. Certain projects require us to implement Microsoft IIS for overall project hosting and delivery. Microsoft IIS is very easy to install, and its GUI is very informative. The Microsoft Server facilitates implementation of SQL database seamless. It is very useful due to its simplicity for small projects which primarily require CRUD operations in SQL.
- Troubleshooting problems is very easy due to the server logs, which are maintained by default in Microsoft IIS.
- Awesome integration with Visual Studio and dot NET applications.
- Best performance with Microsoft tools and services, because of its native nature with them.
- Microsoft IIS' performance, in comparison with lean web-servers like Nginx and Apache, has a lot of room for improvement.
- Since it is a non-open source solution and a proprietary Microsoft software, it is tied with Microsoft Windows OS, which is prone to new security vulnerabilities on a frequent basis.
- The logging of errors is very vague in nature sometimes, which makes it difficult to get to the root cause of the error, and means it takes more time in debugging.
80%
8.0
- The security risk is greater in the case of public facing websites, which impacts the trustworthiness of the solution offered.
- Relatively easy installation boosted productivity for us.
- Tracking down the root cause of a problem takes a long time, which increases the cost and is a very tedious process.
Nginx is hard to support for smaller multiple projects, which is one reason we use the Microsoft IIS server, which is best fit for a set-up once and forget scenario. The Apache server is more recommended for smaller sized projects due to its cost factor, as the Microsoft IIS server turns out to be costly in the initial server setup costs because of the licensing of every proprietary software, including the Windows OS.
No
- Product Usability
- Prior Experience with the Product
The product usability played an important role in selecting the Microsoft IIS Server over other solutions, because of its comparatively simple GUI and simple learning curve when compared to its competitors. Since we needed a very basic website for doing CRUD operations from the SQL database, we implemented the Microsoft IIS Server, which helped us speed up the development process.
I would be more than happy to select it as a preferred server solution if Microsoft considers cutting the cost associated with the Microsoft IIS Server and the other dependencies bundled with it (Microsoft Windows Server OS, Microsoft SQL Server Enterprise, etc), because then it will be more affordable to implement for smaller-sized projects where the cost of management and recurrent costs of subscription plays an important role in decision making.
April 12, 2017
IIS Review
IIS serves a multiplicity of uses for us. It provides internal resources and applications for staff and products for our customer base. The application provides us easy access to multiple internally-developed and vendor-supplied applications for our various internal departments and ready access by our customers to our various products and services.
- Ease of management. IIS is relatively easy to install, configure, monitor and troubleshoot.
- Security. IIS is a large application, with known vulnerabilities and a relatively large attack surface.
- Monitoring and logging. While much of the IIS infrastructure is easily interpreted, more meaningful error messages would be very useful. Arcane event/error messages that are only meaningful to the publisher are not especially useful to a business managing the product.
70%
7.0
- IIS is enabling us to rapidly deploy and maintain new products for our staff and customers. It is difficult to assign an ROI on such efforts, but we have seen improvements in our Net Promoter Scores - both internally and externally - as a result of these efforts.
Two factors drove our implementation of IIS.
1) Staff familiarity. IIS' ubiquity in the marketplace and its' already-familiar developer tools made IIS implementation straightforward.
2) Vendor support. Most of our external software publishers use IIS for their applications. Implementing their solutions using a known platform was simplified.
May 27, 2016
To IIS or not to IIS?
We use IIS in a number of different ways. Some of our homegrown .NET apps run internally on our network as well as several other boxed software installs that require the use of IIS. Our current setup involves about 6 servers all running the latest version of IIS and they seem to be easy to work with and are patched fairly regularly by our staff.
- Very easy to deploy new sites.
- Great integration with Visual Studio .NET.
- Easy to troubleshoot.
- The SQL integration is also fairly seamless.
- It seems like they don't do new version migrations easily. Newer versions of IIS have required that we change our web.config files to exclude certain portions.
- Error messages can be vague if you didn't write them in yourself.
- I would like there to be a way to snapshot instances of IIS without having to snapshot an entire server. Not as a pass/fail test but more as a consistent backup for site hacks and malware.
65%
6.5
- It has provided a free platform to host several of our in house developed applications.
- We have also had to spend a lot of time moving from 6 to 7.5 with code changes that were built into the latest releases.
- When it comes to boxed software we typically choose to load the application on IIS, when given the choice, due to its ease of install and mostly hassle free deployment.
- We have had some difficulty tracking down problems in the past but the newer versions seem to help out more with troubleshooting.
- Apache Tomcat and Nginx
Apache and Nginx are what we use for our large websites and public data. When dealing with the type of traffic we see on our sites IIS just doesn't scale out well. For our staff levels, Apache and Nginx are very hard to support for all of our projects so we can't always use them. IIS seems to fit the bill here for those smaller deployments. Again, it's not my first choice for a lot of connections or for big data. I save those for the Linux servers.